The Deployment of Protocol Stack Components Using Web Services

Multimedia has varying optimal transport methods. The traditional methods employed by transport protocols are to ship all data through identical protocol stacks. An ideal method would transport each media through an optimized stack constructed solely for that medium, allowing improved multimedia QoS to be achieved even at runtime. Dynamically composable protocol stacks overcome the limitations imposed by generic protocol stacks. A dynamically composable protocol stack allows optimization for particular traffic. Here, protocol layers such as real-time G.711 or PCM conversion capabilities could be deployed to address the impedance matching across heterogeneous receivers. Protocol layers are created by the protocol stack (using a Protocol Profiler) according to a properties argument defined when creating an instance of Stack. The SOAP is a lightweight remote procedure calling protocol for the exchange of structured data in a decentralized environment. SOAP enables programs to run and interoperate with other SOAP applications (called Web services) in a distributed environment. The SOAP protocol is based on eXtensible Markup Language (XML) and Hypertext Transmission Protocol (HTTP), which, it is claimed, makes it a languageand platform-neutral vehicle for RPC over the Internet and through firewalls. This paper describes a SOAP Web service deployed on an apache Tomcat server that enables clients to download protocol stack components as MIME attachments. The deployment middleware framework is named Webber. Webber provides additional flexibility that can be extremely useful for environments that have not been considered by standard generic protocols.